Added data_selection support to S3 SQS source#6148
Merged
dlvenable merged 1 commit intoOct 8, 2025
Conversation
dlvenable
requested changes
Oct 8, 2025
dlvenable
left a comment
Member
There was a problem hiding this comment.
Thank you @mzurita-amz for this contribution!
| @Min(1) | ||
| private Integer maxReceiveAttempts; | ||
|
|
||
| @JsonProperty("data_selection") |
Member
There was a problem hiding this comment.
I think we should move this to the root of the configuration. If it is present, then use that for either SQS or scan. We can allow scan options to override this for now.
The sqs configuration is intended to control how the SQS interactions are handled, but this is new configuration is a configuration on how we handle S3.
Contributor
Author
There was a problem hiding this comment.
Moved the configuration to the s3 config. Thanks!
eaa6345 to
ccc4e9e
Compare
Signed-off-by: Manuel Mangas Zurita <mzurita@amazon.com>
037ac0a to
83ace93
Compare
dlvenable
approved these changes
Oct 8, 2025
dlvenable
left a comment
Member
There was a problem hiding this comment.
Thank you @mzurita-amz for this great contribution!
kkondaka
approved these changes
Oct 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Enable SQS-based S3 source to specify whether to process data only, metadata only, or both data and metadata, matching the functionality available in scan-based S3 source.
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.
Testing
Verified the following config produces no S3 metadata